[No QA] Docs updates for E/A#96065 interactive Concierge spend charts - #97738

A preview of your ExpensifyHelp changes have been deployed to https://34bf72a3.helpdot.pages.dev ⚡️

Updated articles:

• articles/new-expensify/concierge-ai/How-Concierge-Analyzes-Spend

HelpDot Documentation Review

Overall Assessment

This PR adds a single new section, How to explore a Concierge spend chart, to the existing How-Concierge-Analyzes-Spend.md article, plus three new keywords (spend chart, bar chart, Concierge chart). The addition documents the interactive bar chart Concierge can return in chat and how users can hover or select a bar to drill into expenses on the Search page. The change is well-scoped, stays within the article's single workflow, and is a clean, additive contribution.

Scores Summary

• Readability: 9/10 - Clear, concise prose with a scannable bullet list and a benefit-focused closing sentence. Minor nit: the intro sentence is slightly long.
• AI Readiness: 8/10 - Heading is task-based and starts with "How to", uses the full feature phrase, and keywords were updated to match real search intent. Heading hierarchy stays at ##. Retrieval readiness is strong.
• Style Compliance: 8/10 - Correctly bolds the Search page reference and uses exact UI terminology. Web-only behavior is stated ("On web, you can interact..."), aligning with the Cross-Platform Clarity Rule. Consider stating explicitly whether chart interaction is available on mobile per the "If a Feature Is Not Available on Mobile" rule, rather than implying it via "On web".

Key Findings

• New ## How to explore a Concierge spend chart heading is task-based and compliant with Section 2 heading rules.
• The Search reference is correctly bolded as a UI destination.
• Web-specific behavior is scoped correctly, but mobile behavior is only implied. Governance requires an explicit statement when a feature is not available on mobile ("This feature is not available on mobile") rather than leaving it inferred.
• Keywords were thoughtfully expanded to match likely user queries (bar chart, spend chart).
• No ### headings, no generic headings, single workflow preserved — clean structure.

Recommendations

• Add an explicit mobile statement if chart interaction is web-only (e.g., "This feature is not available on mobile.") to fully satisfy the platform-clarity rules, instead of relying on "On web".
• Optional: standardize the em dash / curly-quote example for consistency with the rest of the doc.

Files Reviewed

• docs/articles/new-expensify/concierge-ai/How-Concierge-Analyzes-Spend.md — Approved with minor suggestions. New section is well-written, task-based, and correctly scoped; only the implicit mobile-availability wording needs tightening.

Note: Detailed line-by-line feedback has been provided as inline comments.